Geolocation check-in system

ABSTRACT

Embodiments of the invention are directed to systems, methods and computer program products for providing a geolocation check-in system. An exemplary apparatus is configured to collect positioning data related to a user. After collecting position data the apparatus may be configure to determine, based at least partially on the positioning data that the user has crossed a threshold of a geofence associated with a merchant&#39;s location. Based at least partially on this determination the apparatus may be configured to initiate a merchant check-in associated with the user and transmit user information to the merchant.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/826,671, filed Mar. 14, 2013; the contents of which are herebyincorporated by reference.

BACKGROUND

Typically, users are tasked with manually checking in at merchantlocations when they arrive. The current check-in process may cause anadditional delay before the user is able to receive the services whichthe merchant provides. In some instances, where users are able tocheck-in using their mobile device, there is no way to verify that theuser has arrived at the location where they are checking in. At times,users may arrive at merchant locations and not be aware of the merchantcheck-in system that is available for the user. Therefore, there is aneed for a system which allows a user check-in at a merchant locationbased on geolocation data and allows the user to provide the merchantwith pertinent information prior to their arrival.

BRIEF SUMMARY

Embodiments of the invention are directed to systems, methods, andcomputer program products for providing a geolocation check-in system.In some embodiments, the system may comprise an apparatus for providinga geolocation check-in system. The apparatus may comprise severalcomponents, including but not limited to, a memory, a processor, and amodule stored in the memory, executable by the processor, and configuredto perform a plurality of method steps.

In some embodiments, the apparatus is configured to collect positioningdata related to a user. The apparatus may be further configured todetermine, based at least partially on the positioning data, the user'scurrent position. This includes further determining, based at leastpartially on the positioning data, that the user has crossed a thresholdof a geofence associated with a merchant's location. In someembodiments, determining that the user has crossed the threshold of thegeofence further comprises the apparatus being configured to compare theuser's current position to the threshold of the geofence. In someembodiments, the apparatus is further configured to receive one or moreparameters which define the geofence associated with the merchant'slocation.

After determining that the user had crossed a threshold of a geofenceassociated with the merchant's location the system may initiate amerchant check-in associated with the user. In some embodiments,initiating a merchant check-in associated with the user furthercomprises processing a merchant check-in on the user's behalf. In someembodiments, the apparatus is further configured to receive one or moreuser preferences for processing merchant check-ins. In some embodiments,processing a merchant check-in further comprises prompting the user toaccept one or more terms and conditions associated with the merchant.

In some instances user information is transmitted to the merchant inconjunction with processing the merchant check-in on behalf of the user.In some embodiments, the apparatus is further configured to store theuser information. In some embodiments, the apparatus is furtherconfigured to notify one or more entities of a successful merchantcheck-in.

The system may additionally include a computer program product forproviding a geolocation check-in system. In some embodiments, thecomputer program product comprises a set of codes configured to cause acomputer to collect positioning data related to a user. The set of codesmay be further configured to cause a computer to determine, based atleast partially on the positioning data, that the user has crossed athreshold of a geofence associated with a merchant's location. The setof codes may be further configured to cause a computer to initiate amerchant check-in associated with the user. The set of codes may befurther configured to cause a computer to transmit user information to amerchant.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments can be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, where:

FIG. 1 is a diagram illustrating a general geolocation check-in system,in accordance with embodiments of the present invention;

FIG. 2 is a diagram illustrating a geolocation check-in systemenvironment, in accordance with embodiments of the present invention;

FIG. 3 is a flow chart illustrating a general process flow for ageolocation check-in system, in accordance with embodiments of thepresent invention;

FIG. 4 is a flow chart illustrating a general process flow fordetermining a user position, in accordance with embodiments of thepresent invention;

FIG. 5 is a screenshot illustrating a mobile device, in accordance withembodiments of the present invention;

FIG. 6 is a screenshot illustrating a mobile device, in accordance withembodiments of the present invention; and

FIG. 7 is a screenshot illustrating a mobile device, in accordance withembodiments of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention now may be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure may satisfy applicablelegal requirements. Like numbers refer to like elements throughout.

Embodiments of the invention are directed to systems, methods andcomputer program products for providing a geolocation check-in system.The invention enables a user to check-in with a particular merchant inresponse to the user crossing the threshold of a geofenced merchantregion. The invention further provides a means for transmittinginformation to the merchant in addition to the checking in with themerchant.

For example, a user may cross a threshold of a geofence associated witha drive-thru restaurant. Upon crossing the threshold of the geofenceassociated with the restaurant the user may be automatically checked insuch that their order is transmitted to the restaurant. To this extent,the user's food will be prepared by the time they arrive at thedrive-thru window.

As used herein, a “merchant” may refer to a manufacturer, retailer,service provider, event provider, warehouse, supplier, and/or the like.In some embodiments, a “merchant” may be a financial institution. Forthe purposes of this invention, a “financial institution” may be definedas any organization, entity, or the like in the business of moving,investing, or lending money, dealing in financial instruments, orproviding financial services. This may include commercial banks,thrifts, federal and state savings banks, savings and loan associations,credit unions, investment companies, insurance companies and the like.

In some embodiments, the merchant may allow a user to establish anaccount with the merchant. An “account” may be the relationship that theuser has with the merchant. Examples of accounts include a non-monetaryuser profile that includes only personal information associated with theuser, a deposit account, such as a transactional account (e.g., abanking account), a savings account, an investment account, a moneymarket account, a time deposit, a demand deposit, a pre-paid account, acredit account, or the like. The account is associated with and/ormaintained by the merchant.

As used herein a “user” refers to a previous consumer or a non-consumerof one or more merchants or entities. In some embodiments, the “user”may be a user (e.g., an account holder or a person who has an account(e.g., banking account, credit account, or the like) at the entity) orpotential user (e.g., a person who has submitted an application for anaccount, a person who is the target of marketing materials that aredistributed by the entity, a person who applies for a loan that not yetbeen funded). It should be noted that the terms user, user, and/orconsumer may be used interchangeably throughout the specification.

Although embodiments of the present invention described herein aregenerally described as involving a merchant, it will be understood thatthe merchant may involve one or more persons, organizations, businesses,institutions and/or other entities such as financial institutions,services providers and the like that implement one or more portions ofone or more of the embodiments described and/or contemplated herein.

Referring now to FIG. 1, FIG. 1 illustrates a geolocation check-insystem according to an exemplary embodiment of the invention. Asillustrated in FIG. 1, the merchant 210 may be located within at least aportion of a geofenced region such that a user 202 carrying a mobiledevice 204 and the merchant are, initially, at least separated by thethreshold 104 of the geofence 102. The geolocation check-in process maybe initiated in response to the user 202 crossing the threshold 104 ofthe geofence 102 while carrying their mobile device 204. As such, themobile device 204 may serve as an apparatus which provides a means fordetermining the location of the user 202, and in particular determiningthat the user 202 has crossed the threshold 104 of the geofence 102associated with the merchant 210. Initiating the check-in process maylead to one or more subsequent events. This may include the merchant 210receiving a notification that the user 202 has arrived or successfullychecked in. This may additionally include exchanging information betweenthe user 202 and the merchant 210 by transmitting information with theuse of the mobile device 204 to a merchant system 208.

As illustrated in FIG. 1, the merchant 210 is associated with ageofenced region 102. As used herein, a geofence 102 may refer to avirtual perimeter which encompasses a real-world geographic area such asthe merchant location. It should be noted that the terms “geofence” and“geofenced region” may be used interchangeably throughout thespecification. FIG. 1 further illustrates a threshold 104 of thegeofence 102. As used herein, a threshold 104 may refer to the outermostperimeter of the geofenced region 102. In some embodiments, the geofence102 only includes the parameters of the merchant location and/orbuilding itself. To this extent, in such an embodiment, a user 202 maycross the threshold 104 of the geofence 102 upon entering the front doorassociated with the merchant building. In other embodiments, thegeofence includes a region that is associated with the merchant. Thismerchant region may include, but not be limited to, the merchantbuilding(s), parking lot(s), parking deck(s), proximate streets, and thelike. To this extent, in such an embodiment, a user 202 may cross thethreshold 104 of the geofence 102 upon entering the parking lotassociated with the merchant building. For example, the merchant 210 maybe an educational institution having a plurality of buildings. Thus thegeofenced merchant region may be defined by a perimeter whichencompasses more than one building.

In the embodiment illustrated in FIG. 1, the entire merchant building islocated within the geofenced region 102. However, it should be notedthat in other embodiments only a portion of the merchant building may belocated within the geofenced region 102. For the purpose of thisinvention the merchant building and/or location only needs to be atleast partially encompassed by the geofenced region 102. To this extent,at least a portion of the merchant building may be located outside ofthe geofenced region 102. It should be further noted that in otherembodiments, the geofenced region 102 may not include any physicalbuildings. For example, the geofenced region 102 may encompass a generalarea associated with a merchant location such as a park that is void ofphysical structures.

Referring now to FIG. 2, a geolocation check-in system environment 200,in accordance with one embodiment of the present invention, isillustrated. As shown, the merchant system 208 is capable of sendingand/or receiving information from the application server 206. Likewise,the application server 206 is capable of sending and/or receivinginformation from the mobile device 204. This communication may occuracross the network 201. The network 201 may be a global area network(GAN), such as the Internet, a wide area network (WAN), a local areanetwork (LAN), or any other type of network or combination of networks.The network 201 may provide for wireline, wireless, or a combinationwireline and wireless communication between devices on the network.

The application server 206 may include a processing device 234. As usedherein, the term “processing device” generally includes circuitry usedfor implementing the communication and/or logic functions of theparticular system. For example, a processing device may include adigital signal processor device, a microprocessor device, and variousanalog-to-digital converters, digital-to-analog converters, and othersupport circuits and/or combinations of the foregoing. Control andsignal processing functions of the system are allocated between theseprocessing devices according to their respective capabilities. Theprocessing device may include functionality to operate one or moresoftware programs based on computer-readable instructions thereof, whichmay be stored in a memory device.

The application server 206 may further include a communication device232 that is operatively coupled to the processing device 234. Thecommunication device 232 is capable of sending user information to themobile device 204 and/or merchant system 208 in response to determiningthat the user 202 has crossed the threshold 102 of the geofence 104. Theprocessing device 234 uses the communication device 232 to communicatewith the network 201 and other devices on the network 201, such as, butnot limited to, the merchant system 208 and the mobile device 204. Thecommunication device 232 generally comprises a modem, server, or otherdevice for communicating with other devices on the network 201.

The processing device 234 is also operatively coupled to the memorydevice 236. The memory device 236 may house computer-readableinstructions 240 which may include a server application 242. In someembodiments, the memory device 236 includes data storage 238 for storingdata related to the geolocation check-in system environment 200including, but not limited to, data used by the server application 242,or information provided by the user 202, mobile device 204, and/ormerchant system 208. For example, the data storage 238 may store alluser information received from the mobile device 204. The serverapplication 242 may then send the stored user information to themerchant system 208.

The application server 206 may be operatively coupled over a network 201to the mobile device 204, and, in some embodiments, to the merchantsystem 208. The merchant system 208 may include an end system and/orinterface used by a business, such as a computer terminal. It shouldalso be noted, in some embodiments the mobile device 104 may beinterchanged with other end consumer systems, such as a computer. Inthis way, the application server 206 can send information to and receiveinformation from the mobile device 204 and the merchant system 208 toprocess a user check-in with the merchant 208 based on geolocation data.FIG. 2 illustrates only one example of an embodiment of a geolocationcheck-in system environment 200, and it will be appreciated that inother embodiments one or more of the systems, devices, or servers may becombined into a single system, device, or server, or be made up ofmultiple systems, devices, or servers.

In the embodiment illustrated in FIG. 2, the server application 242 mayenable the user 202 and/or the merchant 210 to interact with the system.First, the server application 242 enables a user 202 to receiveinformation based on his/her geographic location proximate to themerchant 210, via the mobile device 104. Next, the server application142 enables the merchant 210 to manually provide information related toa user check-in, via the merchant system 208. The server application 242may be capable of sending and/or receiving information to and from themobile device 204 and the merchant system 208. For example, a mobiledevice 204 may indicate that the user 202 has crossed the threshold 104associated with the geofence 102 of a particular merchant location. Oncenotified, the merchant may send a request for user information that isdelivered to the mobile device 204 via the application server 206. Uponreceiving the user information the merchant 210 may additionally send aconfirmation message that the user 202 has been successfully checked inthat is delivered to the mobile device 204 via the application server206.

In some embodiments, the server application 242 may enable or allow theuser 202 to communicate information, using the mobile device 204,related to the user's presence in a location based on the geolocationdata provided by the mobile application 222. The information sent fromthe mobile device 204 may be sent in response to the user 202 crossingthe threshold 104 of a geofence 102 while carrying their mobile device204. In some embodiments, the mobile device 204 may send userinformation related to checking in with a merchant where the user 202 iscurrently located. In some embodiments, the user 202 may receive, inresponse to the sending the information, a confirmation message that theuser 202 has successfully checked in with the merchant 210. Theconfirmation message may include various information such as thelocation where the user was checked in, the check-in time, a summary ofthe information sent, and/or the like. A similar confirmation messagemay be sent to the merchant 210 and subsequently stored on the merchantsystem 208. The confirmation message may be sent from the merchantsystem 208 to the mobile device 204 using the application server 206 asan intermediate communication device.

An entity, such as a business, may use the merchant system 208 toprovide the server application 242 with information and/or data forinclusion in one or more messages related to the user 202 checking inwith the merchant 210. In some embodiments, the message may be aconfirmation that the user 202 has been successfully checked in with themerchant 210. The server application 242 may also store user informationreceived from the mobile device 204 and subsequently send the userinformation to the merchant system 208. In this way, the serverapplication 242 may have access to user information related to priorcheck-ins, in a database. Thus, the application 242 may need to onlyreceive the user information once and can send merchant 210 userinformation that has been stored in the database for all subsequentcheck-ins related to a particular user 202.

The server application 242 may provide computer readable instructions tothe processing device 234 to match user information stored in the datastorage 238 (which may have previously been, for example, received fromthe mobile device 204 and stored in the data storage 238 of theapplication server 206) with a mobile device 204 of a user 202 based ondetermining the user 202 has crossed the threshold 104 of the geofence102 associated with a merchant location. The server application 242 maythen send the user information to the merchant system 208, using anetwork 101, to initiate a current check in for the user based onpreviously stored user information.

The server application 242 may initiate a check-in for a user 202 basedon one factor or a combination of factors. For example, applicationserver 206 may consider geolocation data provided by the users 202mobile device 204 in determining whether or not to initiate the check-inprocess for a user. Initiating the check-in process may comprise theapplication server 206 sending the user 202 a message to confirm thatthey want to check-in with the merchant 210. The user 202 may bepresented, via mobile device 204, with an option to either decline oraccept checking in with a particular merchant 210 that has indicated theuser 202 has arrived at the merchant location. Initiating the check-inprocess may comprise the application server 206 sending the user 202 arequest to provide additional information related to a check-in with themerchant 210. The user's mobile device 204 may send the applicationserver 206 user information that is either stored on the mobile device204 or has been provided by the user 202. In response, the applicationserver 206 may subsequently send the user information to the merchantsystem 208. In some embodiments, the application server 206 is owned andoperated by the merchant 210. In other embodiments, the applicationserver 206 is owned and operated by a third-party which is independentof the merchant 210.

The merchant system 208 generally includes a communication device 252, aprocessing device 254, and a memory device 256. The processing device254 is operatively coupled to communication device 252, and the memorydevice 256. The merchant system 208 may include an input device such asa keyboard device to receive information from an individual associatedwith the merchant system 208. The merchant system 208 may additionallyinclude a reader device including, but not limited to, a magnetic stripreader, a barcode scanner, a radio frequency (RF) reader, a characterrecognition device, a magnetic ink reader, a processor for interpretingcodes presented over an electrical or optical medium, a biometricreader, a wireless receiving device, and/or the like. In someembodiments, the reading device receives information that may be used tocommunicate instructions via the communication device 252 over a network201, to other systems such as, but not limited to the application server206 and/or other systems. The communication device 252 generallycomprises a modem, server, or other device for communicating with otherdevices on the network 201.

The merchant system 208 includes computer-readable instructions 260stored in the memory device 256, which in one embodiment includes anapplication 262. A merchant system 208 may also refer to any device usedto provide information, messages and/or communicate to be sent to a user202 or the application server 206, including but not limited to,information related to a user 202 checking in with the merchant 210. Insome embodiments, the merchant system 208 may refer only to a pluralityof components. For example, the merchant system 208 may refer to a userdevice, or a user device and a merchant device interacting with oneanother to process a successful merchant check-in.

In some embodiments, the merchant system 208 may serve as an interfacebetween a merchant 210 and the application server 206 or mobile device204 to enable a merchant to provide a user check-in system. In someembodiments, the merchant system 208 is or includes an interactivecomputer terminal that is configured to initiate, communicate, process,and/or facilitate a check-in process for the user 202. A merchant system208 could be or include any device that may be used to communicate witha user 202 or the application server 206, such as, but not limited to, adigital sign, a magnetic-based payment device (e.g., a credit card,debit card, and the like), a personal identification number (PIN)payment device, a contactless payment device (e.g., a key fob), a radiofrequency identification device (RFID) and the like, a computer, (e.g.,a personal computer, tablet computer, desktop computer, server, laptop,and the like), a mobile device (e.g., a smartphone, cellular phone,personal digital assistant (PDA) device, music-playback device, personalGPS device, and the like), a merchant terminal, a self-service machine(e.g., vending machine, self-checkout machine, and the like), a publicand/or business kiosk (e.g., an Internet kiosk, ticketing kiosk, billpay kiosk, and the like), a gaming device, and/or various combinationsof the foregoing.

In some embodiments, the merchant system 208 may be operated in a publicplace (e.g., on a street corner, at the doorstep of a private residence,in an open market, at a public rest stop, and the like). In otherembodiments, the merchant system 208 is additionally or alternativelyoperated in a place of business (e.g., in a retail store, post office,banking center, grocery store, factory floor, and the like). Inaccordance with some embodiments, the merchant system 208 may not beoperated by the user of the merchant system 208. In some embodiments,the merchant system 208 is operated by a mobile business operator or aPOS operator (e.g., merchant, vendor, salesperson, and the like). In yetother embodiments, the merchant system 208 is owned by the entityoffering the merchant system 208 providing functionality in accordancewith embodiments of the invention described herein.

The merchant system 208 application 262 enables the merchant system 208to be linked to the application server 206 to communicate, over thenetwork 201, information related to processing a check-in for the user202. In this way, the application 262 associated with the merchantsystem 208 may provide the application server 242 with variousinformation related to the customized check-in process that is offeredby the merchant 210. In one example, the user 202 enters a businessestablishment, the user's mobile device 204 indicates that the user 202has crossed the threshold 102 of the geofence 104 associated with themerchant location, and sends user information to the application server206, and receives a confirmation message from the application server 206that the user has been successfully checked in by the merchant 210.

The application 262 associated with the merchant system 208 may alsoreceive information from the mobile device 204. The application 262associated with the merchant system 208, in some embodiments, mayreceive an indication that the user 202 has arrived at the merchantlocation, such that the application 262 associated with the merchantsystem 208 may transmit or initiate the transmission of informationrelated to processing a check-in for the user 202.

FIG. 2 also illustrates a mobile device 204. The mobile device 204 mayinclude a communication device 212, a processing device 214, and amemory device 216. The processing device 214 is operatively coupled tothe communication device 212 and the memory device 216. The processingdevice 214 uses the communication device 216 to communicate with thenetwork 201 and other devices on the network 201, such as, but notlimited to, the application server 206 and the merchant system 208. Thecommunication device 216 generally has a modem, server, or other devicefor communicating with other devices on the network 201.

The mobile device 204 may have computer-readable instructions 220 storedin the memory device 216, which in one embodiment includes the userapplication 222. Application 222 may cause the processing device to sendand receive information related to the user's 202 current location,information related to the user 202 crossing a threshold 104 of ageofence 102 associated with a merchant location, user information,and/or information related to the user 202 checking in with the merchant210. The mobile device 204 may also include data storage 218 located inthe memory device 216. The data storage 118 may be used to storeinformation related to information related to the user's 202 currentlocation, the user 202 crossing a threshold 104 of a geofence 102associated with a merchant location, the user 202 checking in with themerchant 210, and/or the like. A “mobile device” 204 may or include anymobile communication device, such as a cellular telecommunicationsdevice (i.e., a cell phone or mobile phone), personal digital assistant(PDA), a mobile Internet accessing device, or other mobile deviceincluding, but not limited to portable digital assistants (PDAs),pagers, mobile televisions, gaming devices, laptop computers, cameras,video recorders, audio/video player, radio, GPS devices, any combinationof the aforementioned, or the like. Although only a single mobile device204 is depicted in FIG. 2, the geolocation check-in system 200 maycontain numerous mobile devices, similar to mobile device 204.

Referring now to FIG. 3, FIG. 3 illustrates a method for providing ageolocation check-in system, in accordance with embodiments of theclaimed invention. The method may comprise one or more steps detailed bythe events listed below. At event 320 positioning data related to theuser 202 is collected in order to determine the users 202 currentposition. Based at least partially on the positioning data, at event340, the system may determine that the user 202 has crossed thethreshold 104 of the geofence 102 associated with the merchant's 210location. At event 360, based at least partially on determining that theuser 202 has crossed the threshold 104 of the geofence 102, the systemmay initiate the process for the user 202 to check-in with the merchant210. At event 380, user information may be transmitted to the merchant210. It should be noted that the following method is not limited to theaforementioned events, and may include one or more additional stepsdiscussed in further detail below. It should be further noted that theaforementioned events may occur in a different order than what isdepicted in FIG. 1, or may occur simultaneously with one another.

FIG. 4 illustrates a general process flow 400 for collecting positioningdata of the user, consistent with embodiments of the present invention,and in particular event 320 of FIG. 1. As represented by block 410, thepositioning data may include global positioning data. Global positioningdata may include any information collected from methods, systems,apparatus, computer programs and the like involving locating a user'sposition relative to satellites, fixed locations, beacons, transmittersor the like. In some instances, global positioning data may be collectedfrom a GPS device, such as a navigation system. Such a navigation systemmay be, but is not limited to, hardware and/or software that are part ofa mobile phone, smartphone, PDA, automobile, watch and the like or acommercially available personal navigation system. The amount, natureand type of the global positioning data that is collected may depend onthe merchant's relationship with the user and the amount of informationthat the user has authorized the merchant or third-party provider tocollect. For instances in some embodiments the global positioning datawill be snapshots of the user's location at different times. Forexample, a snapshot of the user's location may be collected each timethe GPS software, navigation system or application is activated. Theglobal positioning data may also include the destination entered by theuser, recent searches for locations, attractions, addresses and the likeIn other instances, the global positioning data may be the completeroute being provided to the GPS system's user, including destination,route, alternate routes, anticipated time of arrival and the like Insome such embodiments, the global positioning data may include anindication if the user selects a detour from a previously selectedroute, or instructs the navigation system to reach the desired locationtaking specific roads or avoiding certain roads. In instances where theuser's complete route is provided, additional positioning data may notbe necessary to project the route of the user or can be used to confirmthe user is traveling on along the suggested route.

As shown in block 420 of FIG. 2, positioning data of the user mayinclude mobile device data. Mobile device data may include informationregarding the location of the user's mobile device. Such a mobile devicemay include, but is not limited to, a cellular telecommunications device(e.g., a cell phone or mobile phone), personal digital assistant (PDA),smartphone, a mobile Internet accessing device, or other mobile deviceincluding, but not limited to portable digital assistants (PDAs),pagers, gaming devices, laptop computers, tablet computers, and anycombination of the aforementioned, or the like. For instance, thelocation of the mobile phone may be dynamically determined from the cellphone signal and cell towers being accessed by the mobile phone. Inother instances, a mobile device may include software or hardware tolocate the position of the mobile phone from GPS signals, wirelessnetwork locations, and the like. Mobile device data may additionallyinclude data related to the mobile network associated with the mobiledevice. For instance, the system may determine the location of a mobiledevice based on the mobile network towers in which the mobile device iscurrently using. Mobile device data may further include information froman accelerometer that is a part of the mobile device and providesinformation regarding whether the mobile device is moving, and if so, inwhat direction. In some embodiments, mobile device data may be the timeand location of calls placed using the telephone functionality of amobile device. In yet other embodiments, the mobile device data may bedata collected and analyzed by the hardware and/or software of themobile device concerning the surrounding environment. In suchembodiments, hardware, such as a video capture device, camera or thelike and software that is stored in the memory of a mobile devicecaptures a video stream of the environment surrounding the mobile deviceand through object recognition, compass direction, the location of themobile device, and other such data identifies information about theobjects identified in the surrounding environment and/or the environmentitself. For example, in use, a user may use the camera built into hersmartphone to collect a real-time video stream that includes images ofthe facade of a store front and the surrounding area. This image mayinclude the store's name from a marquee, a street address (collectedfrom an image of the numbers on the building and of street signs in thevideo image) and the direction the smartphone is facing (from a compassin the mobile device). Such information may be sufficient to locate theuser's position and potentially the direction the user is facing and/ortraveling.

Referring now to block 430, the positioning data of the user may also becollected from social network data. It will also be understood that“social network” as used herein, generally refers to any socialstructure made up of individuals (or organizations) which are connectedby one or more specific types of interdependency, such as kinship,friendship, common interest, financial exchange, working relationship,dislike, relationships, beliefs, knowledge, prestige, geographicproximity and the like The social network may be a web-based socialstructure or a non-web-based social structure. In some embodiments, thesocial network may be inferred from financial transaction behavior,mobile device behaviors, and the like The social network may be anetwork unique to the invention or may incorporate already-existingsocial networks as well as any one or more existing web logs or “blogs”forums and other social spaces. Social network data may indicate theuser's recent, present or future location through expressed data. Forinstance, a user may upload a blog post, comment on a connection's page,send a friend an electronic message and the like that she is travelingto a specific location or that she is currently in a specific city, oron a specific road and the like Moreover, many already-existing socialnetworks provide users with the ability to “check-in”, “flag” orotherwise indicate the user's current location. Accordingly, userpositioning data collected from social networking data may consist ofsuch indications. Furthermore, many social networks allow users to rate,like, comment and the like on restaurants, attractions, locations andthe like. Accordingly, a user may indicate that she ate at a certainrestaurant or business at a given time and thereby provide informationabout her location at that time. Furthermore, a user may uploadphotographs to a social networking site and thereby provide informationabout the user's location. In some instances the user's location may bedetermined from the picture, (for example a picture of a state linesign, a highway sign, a mile marker and the like) or a captionassociated with the picture may indicate the user's location and/or thetime the photo was taken.

As shown in block 440, the positioning data of the user may also becollected from Internet data. Internet data, may include any informationrelating to the searches conducted by the user, website's visited by theuser and the like that suggests the user's present or futurelocation(s). For instance, in preparing for a vacation a user mayconduct searches for hotels, restaurants or activities in the area wherethe user will be staying. Similarly, a user may review weather forecastsfor locations other than her place of residence indicating that she maysoon be traveling to that location. A user may also search forconstruction or traffic reports indicating future travel along certainroads. Moreover, changes in search patterns may suggest a user's futurelocation. For instance if a user usually uses a web browser applicationjust to read online news articles or to check sports scores but suddenlybegins to search for camping gear, hiking manuals and boots it may beindicative that the user is anticipating taking a hiking trip and willbe traveling away from her home area. It will be understood that suchInternet data may relate to searches or websites visited by the userbefore she began traveling, however, inasmuch as many mobile devicesalso include mobile Internet connectivity, it will also be understoodthat such information may be dynamically collected as the user travels.

As shown by block 450, once the positioning data of the user iscollected from one or more of the global positioning data 410, mobiledevice data 420, social network data 430 and Internet data 440, thepositioning data is analyzed to determine the user's 202 currentposition. It will be understood that the positioning data may be datathat is available directly to the mobile device 204, the merchant 208,or data that is collected by other merchants or a third-party serviceprovider and then provided to the merchant.

In some embodiments, analyzing the position data to determine the user'sposition further comprises analyzing the positioning data to project theuser's likely route of travel and anticipate a user's check-in. Forexample, in use, a user in New York City may engage in a transactionconsisting of using a credit card to pay a cab fare. The user's GPSdevice on her mobile phone, or a phone call placed around the same time,may indicate that she is still in New York but a review of her socialnetworking data indicates she has checked-in on her social networkingpage at La Guardia International Airport. Internet data from the user'smobile phone indicates that she has recently checked the weather anumber of times in San Diego, Calif. Based on this information, thesystem may determine that the user is likely traveling by plane from NewYork to San Diego and anticipate the user checking at an airport in SanDiego. As such the system may send the merchant 208 a notificationindicating the user is in route to the merchant 202. In response toanticipating a user's 202 arrival the system may further monitor for theuser 202 to cross the threshold 104 of the geofence 102 associated withthe merchant 208.

In some instances in projecting the user's likely route of travel, theprojection will be based on the information currently being collected,e.g. the user's current GPS location, the most recent social network andInternet search data and the like In other instances, the current datawill be combined with historical positioning data to project the user'slikely route of travel. For instance, if historical positioning dataindicates that when the user leaves her home traveling south bound andthen turns onto a specific highway, ninety percent of the time she istraveling to the beach, this information might be used in the future toproject the user's likely route of travel when she begins to follow asimilar route. Similarly, the positioning data being currently collectedabout the user may be combined with information regarding the travelpatterns of other users in similar situations to project the user'slikely route of travel. For instance, if the user is a youngprofessional of a known income level and the current positioning dataindicates that the user is traveling west on an interstate at 5:00 p.m.on a Friday afternoon, this data may be combined with informationconcerning the travel patterns of other young professionals with similarincome levels to identify a likely route of travel and anticipate theuser checking in at a business meeting.

In some embodiments, determining that the user 202 has crossed athreshold 104 of the geofence 102, at event 340, further comprisescomparing the positioning data and/or the users 202 current position tothe threshold 104 of the geofence 102. In one embodiment, the threshold104 of the geofence 102 may be defined by a plurality of points, wherethe points may be latitude/longitude coordinate pairs. The system 200may continuously monitor the users 202 current position in comparison toone or more points and determine that the user 202 has crossed athreshold 104 of the geofence 102 when at least one point is equivalentto the current position of the user 202. In other embodiments, thesystem may establish a first and second region, where the first regionis equivalent to the geofenced region 102 and the second region is anygeographic area that is not included in the geofenced region 102, anddetermine that the user 202 has crossed a threshold 104 of the geofence102 when the current position of the user 202 is equivalent to a pointwithin the first region.

In some embodiments, determining that the user determining that the user202 has crossed a threshold 104 of the geofence 102, at event 340,further comprises sending one or more entities and alert and/ornotification message indicating that the user 202 has crossed athreshold 104 of the geofence 102. The alert and/or notification messagemay include, but not be limited to, text messages, multimedia messages,email messages, and/or the like.

In some embodiments, determining that the user 202 has crossed athreshold 104 of the geofence 102 further comprises defining thegeofenced region 102. It should be noted that although, in someembodiments, determining that the user 202 has crossed the threshold 104at event 340 occurs subsequent to collecting positioning data at event320, the geofenced region 102 may be defined prior to collecting thepositioning data at event 320. The geofence 102 may be defined by one ormore entities, including but not limited to, a merchant 210, a user 202,or a third-party not associated with either the merchant or the user.Defining a geofence 102 may comprise an entity providing one or moreparameters which specify the geographic area and/or region which thegeofence 102 encompasses. The one or more parameters which define thegeofenced region 102 may be received by the mobile device 202,application server 206, and/or the merchant system 208. Defining ageofence 102 may also comprise the geofence being embodied by aplurality of shapes. For example, the geofence 102 may be circular,rectangular, a polygon, an organic shape, a street linked shape, and/orthe like. For example, the geofence 102 may be a closed polygon definedover a geographical area. The geofence 102 may be defined as either anarea of inclusion or an area of exclusion.

In some embodiments, the geofence 102 is explicitly defined. Forexample, the geofence 102 may be defined by one or morelatitude/longitude coordinate pairs. In such an embodiment eachcoordinate may form a corner of the geofence 102. In an embodiment wherethe geofence 102 is circular, the geofence 102 may be defined by alatitude/longitude coordinate pair which specifies the center point ofthe geofence 102 and a radius and/or diameter which specifies the lengthto which the region extends from the center point of the geofence 102.The number of coordinates required may vary depending on the type ofgeofence 102. In another example, the geofence 102 may be defined by oneor more streets on which the merchant 210 is either located orsurrounded by.

In other embodiments, the geofence 102 is inexplicitly defined. Forexample, the geofence 102 may be defined by an organic shape which isdrawn on a map and specifies a region in which the merchant 210 islocated. In such an embodiment, the system may be further configured todetermine based on the organic shape one or more latitude/longitudecoordinate pairs which define the geofence 102.

Defining the geofence 102 may comprise the system prompting and/orrequesting and/or requesting an entity such as the user 202 or themerchant 210 to provide information related to specifying the region tobe associated with the geofence 102. For example, the system may promptthe entity to enter one or more latitude/longitude coordinate pairswhich define the geofence 102. In another example, as illustrated inFIG. 5, the system may request the entity to draw on a map a regionwhich defines the geofence 102. In yet another example, the system mayrequest the entity to specify one or more streets on which the merchant210 is either located or surrounded by. As further illustrated in FIG.5, when defining the geofence 102 of the Emergency Room, the entity mayspecify that the geofenced is defined by the boundaries of ‘A’ Street,‘C’ Street, and ‘D’ Street.

In some embodiments, defining the geofenced region 102 may furthercomprise verifying and/or determining that the defined region isaccurate. For example, if a geofence 102 is defined by the user 202, themerchant 210 may subsequently verify that the merchant 210 location isindeed within the defined region. In another example, the geofence 102may be defined by the merchant. Upon receiving a notification, on theirmobile device 204, that the user 202 has crossed the threshold 104 ofthe geofence 102 the user 202 may indicate that they are not at themerchant location 606, as illustrated in FIG. 6. Determining that ageofenced region 102 is either accurate and/or inaccurate may furthercomprise notifying one or more entities geofenced region 102 is eitheraccurate and/or inaccurate, via a message or the like. If it isdetermined that the geofenced region 102 is not accurate the system mayrequest an entity, that is either responsible for defining the geofence102 or determining the geofence 102 is inaccurate, to redefine thegeofenced region 102. For example, the system may prompt the entity toenter one or more latitude/longitude coordinate pairs which redefine thegeofenced region 102.

The parameters of a geofence 102 may be stored in various locations. Forexample, the parameters of the geofence may be stored on the mobiledevice 204, application server 206, merchant system 208, a dynamic GPSsystem (which may be accessed by any device within the system 200), athird-party system, and/or the like. In some embodiments, the parametersof the geofence 102 are stored in the memory 216 of the mobile device204. For example, the mobile device 204 may compare the users 202current position to the parameters of the geofence 102, which are storedin the memory 216, to determine that the user 202 has crossed thethreshold 104 of the geofence 102. The mobile device 204 mayalternatively transmit the users 202 current position and the parametersof the geofence 102, which are stored in the memory 216, to a seconddevice, such as the application server 206, for the second device todetermine that the user 202 has crossed the threshold 104 of thegeofence 102. In an instance that a second device determines that theuser 202 has crossed the threshold 104 of the geofence 102, the seconddevice may send a notification message and/or alert to the first device(e.g. mobile device 204) indicating that the user 202 has crossed thethreshold 104 of the geofence 102.

In some embodiments, the parameters of the geofence 102 are stored inthe memory 256 of the merchant system 208. For example, the merchantsystem 208 may receive the users 202 current position from a seconddevice, such as the mobile device 204, and compare the users 202 currentposition to the parameters of the geofence 102, which are stored in thememory 216, to determine that the user 202 has crossed the threshold 104of the geofence 102. The merchant system 208 may alternatively transmitthe parameters of the geofence 102, which are stored in the memory 256,to a second device, such as the application server 206, for the seconddevice to determine that the user 202 has crossed the threshold 104 ofthe geofence 102. In an instance that a second device determines thatthe user 202 has crossed the threshold 104 of the geofence 102, thesecond device may send a notification message and/or alert to the firstdevice (e.g. merchant system 208) indicating that the user 202 hascrossed the threshold 104 of the geofence 102.

In other embodiments, the parameters of the geofence 102 are stored inthe memory 236 of the application server 206. For example, theapplication server 206 may receive the users 202 current position from asecond device, such as the mobile device 204, and compare the users 202current position to the parameters of the geofence 102, which are storedin the memory 236, to determine that the user 202 has crossed thethreshold 104 of the geofence 102. The application server 206 mayalternatively transmit the parameters of the geofence 102, which arestored in the memory 236, to a second device, such as the mobile device204 or the merchant system 208, for the second device to determine thatthe user 202 has crossed the threshold 104 of the geofence 102. In aninstance that a second device determines that the user 202 has crossedthe threshold 104 of the geofence 102, the second device may send anotification message and/or alert to the first device (e.g. applicationserver 206) indicating that the user 202 has crossed the threshold 104of the geofence 102.

In some embodiments, initiating a user check-in with the merchant 210,at event 360, may further comprise automatically checking the user 202in with the merchant 210. The automatic check-in may be initiated basedat least partially on determining that the user 202 has crossed thethreshold 104 of the geofence 102. In an instance where a user 202 isautomatically checked in with a merchant upon crossing the threshold 104of the geofence 102 the system 200 may send the user 202 alert and/ornotification message, via the mobile device 204 which the user iscarrying, indicating that the user 202 has been automatically checked inwith the merchant 210. The alert and/or notification message mayinclude, but not be limited to, text messages, multimedia messages,email messages, and/or the like. The user 202 may opt-in to thefunctionality of automatic check-ins. In an instance, where the user 202has not opted into the functionality for automatic check-in the user 202may be prompted to verify that they want to check in with the merchant210 prior to being checked in. In some embodiments, the user 202 may setpreferences for check-ins. For example, the user 202 may specify thatthey want to be automatically checked in at all merchant locations. Inanother example, the user may specify that they want to be checked in atonly certain merchant locations. In some embodiment, the option forselecting user preferences may be presented as a menu on a displayassociated with the mobile device 204. The menu may comprise a list ofall merchants that the user has previously visited, and the user maycustomize their check-in process for each individual merchant. Inanother embodiment, the menu may present a list of merchant that arewithin the geographic area where the user is currently located.

In some embodiments, initiating a user check-in with the merchant 210,at event 360, may further comprise prompting and/or requesting the user202 to verify that they want to check in with the merchant 210, asillustrated in FIG. 6. Prompting and/or requesting the user 202 toverify that they want to check in with the merchant 210 may be initiatedbased at least partially on determining that the user 202 has crossedthe threshold 104 of the geofence 102. Prompting and/or requesting theuser 202 to verify that they want to check in with the merchant 210 maycomprise presenting on the mobile device 204, which the user iscarrying, a notification 602 indicating the user 202 has entered thegeofence of a particular merchant 210, a request 604 for the user 202 toverify they would like to check in, and/or an option 606 for the user202 to specify the notification 602 is inaccurate. The user 202 mayrespond to the request 604 by either accepting or declining a check-inwith the merchant 210. In an instance where a user 202 declines to bechecked in with a merchant 210 upon crossing the threshold 104 of thegeofence 102 the system 200 may send an alert and/or notificationmessage to an entity (e.g. merchant 210, mobile device 204) indicatingthat the user 202 has declined to be checked in with the merchant 210.In an instance where the user 202 accepts the option to be checked inwith the merchant 210 upon crossing the threshold 104 of the geofence102, the system 200 may send an alert and/or notification message to anentity (e.g. merchant 210, mobile device 204) indicating that the user202 has accepted the option to be checked in with the merchant 210. Thealert and/or notification message may include, but not be limited to,text messages, multimedia messages, email messages, and/or the like.

In some embodiments, checking in with a merchant 210 further comprisesnotifying the user 202 of a successful and/or unsuccessful check-in withthe merchant 210. In some embodiments, checking in with a merchant 210further comprises the user 202 checking in with merchant 210 on one ormore social networks. Checking in with merchant 210 on one or moresocial networks may comprise presenting on the mobile device 204, whichthe user is carrying, a request 604 for the user 202 to verify theywould like to check in with the merchant on one or more social networks.The user 202 may respond to the request 604 by either accepting ordeclining a check-in with the merchant 210 on one or more socialnetworks. Checking in with merchant 210 on one or more social networksmay additionally comprise the user 202 providing one or more loginand/or verification credentials associated with the social network priorto checking in with the merchant 210 on the social network. In otherembodiments, checking in with the merchant 210 on a social network mayoccur simultaneously and/or automatically in conjunction with a generalcheck-in with the merchant 210.

In some embodiments, checking in with a merchant 210 further comprisesthe user 202 accepting one or more terms and conditions associated withthe merchant 210. Accepting one or more terms and conditions associatedwith the merchant 210 may comprise presenting on the mobile device 204,which the user is carrying, a request 604 for the user 202 to acceptand/or decline one or more terms and conditions associated with themerchant 210. The user 202 may respond to the request 604 by eitheraccepting or declining one or more terms and conditions associated withthe merchant 210. In an instance where a user 202 declines to accept oneor more terms and conditions associated with the merchant 210, thesystem 200 may send an alert and/or notification message to an entity(e.g. merchant 210, mobile device 204) indicating that the user 202 hasdeclined to accept one or more terms and conditions associated with themerchant 210. In an instance where the user 202 accepts one or moreterms and conditions associated with the merchant 210, the system 200may send an alert and/or notification message to an entity (e.g.merchant 210, mobile device 204) indicating that the user 202 hasaccepted accept one or more terms and conditions associated with themerchant 210. The alert and/or notification message may include, but notbe limited to, text messages, multimedia messages, email messages,and/or the like.

In some embodiments, user information is not initially stored on adevice within the system. As such, in some embodiments, transmittinguser information to the merchant 210, at event 380, may further compriserequesting the that the user information be provided prior totransmitting the user information. The user information may be providedvia various devices. The user information may be provided via the mobiledevice 204, application server 206, a third-party system, and/or thelike. In some embodiments, the check-in occurs in response to an entityproviding user information. For example, as illustrated in FIG. 7, thesystem 200 may present the user 202 a form, via the mobile device 204,to provide user information and check the user 202 in with the merchant210 in response to the user information being provided. If a devicewithin the system 200 determines that the information provided isinaccurate, the system may subsequently send a notification and/or alertmessage indicated that the check-in was unsuccessful due to inaccurateuser information, requesting that the entity correct the userinformation, and/or a combination of both indicating that the check-inwas unsuccessful due to inaccurate user information and requesting thatthe entity correct the user information such that it is accurate.

In some embodiments, transmitting user information to the merchant 210may further comprise storing the user information. The user informationmay be stored in various locations. The user information may be storedon the mobile device 204, application server 206, merchant system 208, athird-party system, and/or the like. In some embodiments, the userinformation is initially stored in the memory 216 of the mobile device204. For example, the mobile device 204 may initially store the userinformation and transmit the user information, to a second device, suchas the merchant system 208 or application server 206. The userinformation may additionally be subsequently stored in the memory of thesecond device after being transmitted from the mobile device 204. Insome embodiments, the user information is transmitted to the merchant210 directly from the mobile device 204. For example, the userinformation may be stored in the memory 216 of the mobile device 204 anddirectly transmitted to the merchant system 208, via the communicationdevices 212, 252. In other embodiments, the user information istransmitted to the merchant 210 indirectly from the mobile device 204.For example, the user information may be stored in the memory 216 of themobile device 204 and transmitted the application server 206, via thecommunication devices 212, 232. The user information may then betransmitted from the application server 206 to the merchant system 208,via the communication devices 232, 252.

In some embodiments, the user information is initially stored in thememory 236 of the application server 206. For example, the applicationserver 206 may initially store the user information and transmit theuser information, to a second device, such as the merchant system 208.The user information may additionally be subsequently stored in thememory of the second device after being transmitted from the applicationserver 206. In some embodiments, the user information is transmitted tothe merchant 210 directly from the application server 206. For example,the user information may be stored in the memory 236 of the applicationserver 206 and directly transmitted to the merchant system 208, via thecommunication devices 232, 252. In other embodiments, the userinformation is transmitted to the merchant 210 indirectly from theapplication server 206. For example, the user information may be storedin the memory 216 of the application server 206 and transmitted themobile device 204, via the communication devices 232, 212. The userinformation may then be transmitted from the mobile device 204 to themerchant system 208, via the communication devices 212, 252. In someembodiments, the user information is transmitted to multiple devices.For example, the user information may comprise flight information whichis stored on an application server 206 associated with the airlines suchthat the user information is transmitted to the mobile device 204 andthe merchant system 208 associated with the airlines, in response to theuser 202 crossing the threshold 104 of the geofence 102 associated withthe airport.

In some embodiments, transmitting user information the merchant 210, atevent 380, may further comprise automatically transmitting userinformation the merchant 210. The automatic transmission of userinformation may be initiated in response to a user check-in with themerchant. In an alternative embodiment, an automatic check-in with themerchant occurs in response to the transmission of user information. Theautomatic transmission of user information may also be initiated inresponse to a request for the user information to be transmitted. In aninstance where a user information is automatically transmitted thesystem 200 may send the user 202 alert and/or notification message, viathe mobile device 204 which the user is carrying, indicating that theuser information has been automatically transmitted to the merchant. Thealert and/or notification message may include, but not be limited to,text messages, multimedia messages, email messages, and/or the like. Theuser 202 may opt-in to the functionality for automatically transmittingof user information. In an instance, where the user 202 has not optedinto the functionality for automatically transmitting user informationthe user 202 may be prompted to verify that they want to transmit userinformation to the merchant 210 prior to the user information beingsent. In some embodiments, the user 202 may set preferences forautomatically transmitting user information. For example, the user 202may specify that they want their user information to be automaticallytransmitted at all merchant locations. In another example, the user mayspecify that they only want their user information to be automaticallytransmitted at certain merchant locations.

In some embodiments, transmitting user information to the merchant 210,at event 380, may further comprise prompting and/or requesting the user202 to verify that they want to transmit user information to themerchant 210. Transmitting user information to the merchant 210 may beinitiated based at least partially on determining that the user 202 hascrossed the threshold 104 of the geofence 102. Transmitting userinformation to the merchant 210 may comprise presenting on the mobiledevice 204, which the user is carrying, a notification 602 indicatingthe user 202 has entered the geofence of a particular merchant 210 and arequest 604 for the user 202 to verify they would like to transmit userinformation to the merchant 210. The user 202 may respond to the request604 by either accepting or declining to transmit user information to themerchant 210. In an instance where a user 202 declines to transmit userinformation to the merchant the system 200 may send an alert and/ornotification message to an entity (e.g. merchant 210, mobile device 204)indicating that the user 202 has declined to transmit user informationto the merchant 210. In an instance where the user 202 accepts theoption to transmit user information to the merchant 210 the system 200may send an alert and/or notification message to an entity (e.g.merchant 210, mobile device 204) indicating that the user 202 hasaccepted the option to transmit user information the merchant 210. Thealert and/or notification message may include, but not be limited to,text messages, multimedia messages, email messages, and/or the like.

In some embodiments, the user information may comprise one or moreencryption and/or decryption keys related to information beingtransmitted. As such the information may be encrypted prior to beingtransmitted to the merchant, and the merchant may additionally receive akey for decrypting the user information that is received. In someembodiments, the user information may comprise one or more securityand/or authorization keys. For example, the authorization key may accessa gate associated with the user's apartment complex. As such, when theuser crosses the threshold associated with the apartment the system maytransmit the authorization key to the apartment complex and the gate maybe opened in response.

Any of the features described herein with respect to a particularprocess flow are also applicable to any other process flow. Inaccordance with embodiments of the invention, the term “module” withrespect to a system may refer to a hardware component of the system, asoftware component of the system, or a component of the system thatincludes both hardware and software. As used herein, a module mayinclude one or more modules, where each module may reside in separatepieces of hardware or software.

Although many embodiments of the present invention have just beendescribed above, the present invention may be embodied in many differentforms and should not be construed as limited to the embodiments setforth herein; rather, these embodiments are provided so that thisdisclosure will satisfy applicable legal requirements. Also, it will beunderstood that, where possible, any of the advantages, features,functions, devices, and/or operational aspects of any of the embodimentsof the present invention described and/or contemplated herein may beincluded in any of the other embodiments of the present inventiondescribed and/or contemplated herein, and/or vice versa. In addition,where possible, any terms expressed in the singular form herein aremeant to also include the plural form and/or vice versa, unlessexplicitly stated otherwise. Accordingly, the terms “a” and/or “an”shall mean “one or more,” even though the phrase “one or more” is alsoused herein. Furthermore, when it is said herein that something is“based on” something else, it may be based on one or more other thingsas well. In other words, unless expressly indicated otherwise, as usedherein “based on” means “based at least in part on” or “based at leastpartially on.” Like numbers refer to like elements throughout. Likenumbers refer to like elements throughout.

As will be appreciated by one of ordinary skill in the art in view ofthis disclosure, the present invention may include and/or be embodied asan apparatus (including, for example, a system, machine, device,computer program product, and/or the like), as a method (including, forexample, a business method, computer-implemented process, and/or thelike), or as any combination of the foregoing. Accordingly, embodimentsof the present invention may take the form of an entirely businessmethod embodiment, an entirely software embodiment (including firmware,resident software, micro-code, stored procedures in a database, or thelike), an entirely hardware embodiment, or an embodiment combiningbusiness method, software, and hardware aspects that may generally bereferred to herein as a “system.” Furthermore, embodiments of thepresent invention may take the form of a computer program product thatincludes a computer-readable storage medium having one or morecomputer-executable program code portions stored therein. As usedherein, a processor, which may include one or more processors, may be“configured to” perform a certain function in a variety of ways,including, for example, by having one or more general-purpose circuitsperform the function by executing one or more computer-executableprogram code portions embodied in a computer-readable medium, and/or byhaving one or more application-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, electromagnetic, infrared, and/orsemiconductor system, device, and/or other apparatus. For example, insome embodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as, forexample, a propagation signal including computer-executable program codeportions embodied therein.

One or more computer-executable program code portions for carrying outoperations of the present invention may include object-oriented,scripted, and/or unscripted programming languages, such as, for example,Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript,and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

Some embodiments of the present invention are described herein withreference to flowchart illustrations and/or block diagrams of apparatusand/or methods. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and/or combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions. These one or more computer-executable program code portionsmay be provided to a processor of a general purpose computer, specialpurpose computer, and/or some other programmable data processingapparatus in order to produce a particular machine, such that the one ormore computer-executable program code portions, which execute via theprocessor of the computer and/or other programmable data processingapparatus, create mechanisms for implementing the steps and/or functionsrepresented by the flowchart(s) and/or block diagram block(s).

The one or more computer-executable program code portions may be storedin a transitory and/or non-transitory computer-readable medium (e.g., amemory or the like) that can direct, instruct, and/or cause a computerand/or other programmable data processing apparatus to function in aparticular manner, such that the computer-executable program codeportions stored in the computer-readable medium produce an article ofmanufacture including instruction mechanisms which implement the stepsand/or functions specified in the flowchart(s) and/or block diagramblock(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with, and/or replaced with,operator- and/or human-implemented steps in order to carry out anembodiment of the present invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of and not restrictive on the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations, modifications, andcombinations of the just described embodiments can be configured withoutdeparting from the scope and spirit of the invention. Therefore, it isto be understood that, within the scope of the appended claims, theinvention may be practiced other than as specifically described herein.

What is claimed is:
 1. An apparatus for providing a geolocation check-insystem, the apparatus comprising: a memory; one or more processors; anda module stored in the memory, executable by the one or more processors,and configured to cause the one or more processors to: determine alikely route of travel of a user, wherein determining the likely routeof travel is determined based on analyzing social network feedsassociated with the user, wherein the social network feeds provide anindication of the likely route of travel of the user; collect, from acomputing device associated with the user, positioning data related tothe user, wherein the positioning data comprises a location of the useralong the likely route of travel, and wherein the positioning data isdetermined by the computing device interfacing with a global positioningsystem; identify a threshold of a geofence associated with a merchant'slocation; determine whether the likely route of travel of the user willcross the threshold of the geofence associated with the merchant;determine, based at least partially on the positioning data, that theuser has crossed the threshold of the geofence associated with themerchant's location; transmit a communication to the user requesting theuser to check-in with a social media site associated with the merchant;receive a verification that the user desires to check-in with themerchant; initiate a check-in with the social network associated withthe merchant; and transmit information associated with the user to themerchant.
 2. The apparatus of claim 1, wherein determining that the userhas crossed the threshold of the geofence further comprises theapparatus being configured to compare the user's current position to thethreshold of the geofence.
 3. The apparatus of claim 1, wherein theapparatus is further configured to receive one or more user preferencesfor processing check-ins with a social network associate with amerchant.
 4. The apparatus of claim 3, wherein processing the check-inwith the social network associated with the merchant further comprisesprompting the user to accept one or more terms and conditions associatedwith the merchant.
 5. The apparatus of claim 1, wherein the apparatus isfurther configured to store the user information.
 6. The apparatus ofclaim 1, wherein the apparatus is further configured to notify one ormore entities of a successful check-in.
 7. The apparatus of claim 1,wherein the positioning data further comprises data from a video streamof an environment surrounding the user, wherein the video stream iscaptured by the computing device associated with the user.